Fix reading tags when repository has been transferred to another user #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
thanks a lot for your work. can you update the code to support Stata 14 and up? |
DONE! Unless I am doing something wrong, I changed to Best, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear @haghish ,
First of all, thank you so much for the
githubcommand. It is fantastic. I think it will revolutionize the way people work and contribute in Stata.Problem
I found an issue with
github querywhen a repo has been transferred to a new user. My understanding of the problem is that the Github API returns values in a different order when the repo has been transferred. In the first image below, the current version ofgithubworks fine when I query the original repopip-technical-team/pip, but It fails when I call the new official repo,worldbank/pip(second image).working fine
Failing
Solution
In this PR, I made some modifications so it always reads the tags correctly.
Best,